Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c7e5592ed7fc2eef09e6490d58f1ef413936a5b5575a792e650fd876f4a831f

Tx prefix hash: 9aa26a47a1e94f69799c1671c42d041cad8029bccd9532a0b368815474bb92f4
Tx public key: 763517a968e13267b24676f92d704a642d3f433ae8c5fd2b6793c6f836dcc368
Timestamp: 1658772647 Timestamp [UCT]: 2022-07-25 18:10:47 Age [y:d:h:m:s]: 03:098:07:20:28
Block: 551569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 850043 RingCT/type: yes/0
Extra: 01763517a968e13267b24676f92d704a642d3f433ae8c5fd2b6793c6f836dcc3680211000000026570b1ef000000000000000000

1 output(s) for total of 9.128997030000 dcy

stealth address amount amount idx
00: f1b40f72a4716be042720e3c499058398aa78dbf5bff13c3571a962ab78da550 9.128997030000 983195 of 0

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": 551579, "vin": [ { "gen": { "height": 551569 } } ], "vout": [ { "amount": 9128997030, "target": { "key": "f1b40f72a4716be042720e3c499058398aa78dbf5bff13c3571a962ab78da550" } } ], "extra": [ 1, 118, 53, 23, 169, 104, 225, 50, 103, 178, 70, 118, 249, 45, 112, 74, 100, 45, 63, 67, 58, 232, 197, 253, 43, 103, 147, 198, 248, 54, 220, 195, 104, 2, 17, 0, 0, 0, 2, 101, 112, 177, 239, 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