Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1d9ad9e24dcdb2daa39b8a7c417879a05fbee352ec2abb529044fdb187d5966

Tx prefix hash: b59d96cdd29f70b58e263768543714e059ccd8c233005a89b04f44a2098dbf8b
Tx public key: f1c703db18f648455dfa877766a1df2416ad15265af2d0914593a2f2e3b1f379
Timestamp: 1725011587 Timestamp [UCT]: 2024-08-30 09:53:07 Age [y:d:h:m:s]: 00:291:16:03:30
Block: 1099101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208235 RingCT/type: yes/0
Extra: 01f1c703db18f648455dfa877766a1df2416ad15265af2d0914593a2f2e3b1f37902110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd8e699434a7456d1184ee898fc92fee0f0db6a6747ad2aa2737f501d7fb6767 0.600000000000 1575028 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": 1099111, "vin": [ { "gen": { "height": 1099101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd8e699434a7456d1184ee898fc92fee0f0db6a6747ad2aa2737f501d7fb6767" } } ], "extra": [ 1, 241, 199, 3, 219, 24, 246, 72, 69, 93, 250, 135, 119, 102, 161, 223, 36, 22, 173, 21, 38, 90, 242, 208, 145, 69, 147, 162, 242, 227, 177, 243, 121, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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