Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc51715313d240e377bdde029ac55c5a666223ade628db905c7240fbf416a44b

Tx prefix hash: 9dcca0ce48b7ffc5fd356b06c50a059f2f57a5b3161e36daddeb510836f6fb9b
Tx public key: 7b7596ef1b98aa4e5cb05844b25b99da02190688f81affbcb1b35cc35c0a8d13
Timestamp: 1738441075 Timestamp [UCT]: 2025-02-01 20:17:55 Age [y:d:h:m:s]: 00:292:02:08:49
Block: 1210002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206528 RingCT/type: yes/0
Extra: 017b7596ef1b98aa4e5cb05844b25b99da02190688f81affbcb1b35cc35c0a8d13021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7259a45cc035d9db8269bbca9caf10a5d03fa9b34e26948f5d5fbc1429aaf75b 0.600000000000 1696749 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": 1210012, "vin": [ { "gen": { "height": 1210002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7259a45cc035d9db8269bbca9caf10a5d03fa9b34e26948f5d5fbc1429aaf75b" } } ], "extra": [ 1, 123, 117, 150, 239, 27, 152, 170, 78, 92, 176, 88, 68, 178, 91, 153, 218, 2, 25, 6, 136, 248, 26, 255, 188, 177, 179, 92, 195, 92, 10, 141, 19, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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