Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 661463468af7af8b802f5b8b4eafa20087197deceff5b58ac5efc74418f29e49

Tx prefix hash: 8dd3b5e4d0ffc4479f736c13fad38b4e048c4a3f44bfb645520f386a9284a4b7
Tx public key: 409688e3d890b6e3df95d4ac0ba34027b7f1cc06c07054804a1e755f693ca84e
Timestamp: 1702679064 Timestamp [UCT]: 2023-12-15 22:24:24 Age [y:d:h:m:s]: 01:188:03:31:19
Block: 913950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395488 RingCT/type: yes/0
Extra: 01409688e3d890b6e3df95d4ac0ba34027b7f1cc06c07054804a1e755f693ca84e02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b40e9272e00fd074578ce8208533747ddb02c87e632323bfc980b65a9286a12 0.600000000000 1371230 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 913960, "vin": [ { "gen": { "height": 913950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b40e9272e00fd074578ce8208533747ddb02c87e632323bfc980b65a9286a12" } } ], "extra": [ 1, 64, 150, 136, 227, 216, 144, 182, 227, 223, 149, 212, 172, 11, 163, 64, 39, 183, 241, 204, 6, 192, 112, 84, 128, 74, 30, 117, 95, 105, 60, 168, 78, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8