Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8dfbd7aea4b59edb107a74f6fd1308c1d10c133d210ee5698878c02ee2bb6e9

Tx prefix hash: c68c6b7fc51bb633309ab8fbcd427e683a567f5c30d2198cb1f8104cd3b8cd4c
Tx public key: 43667d3344de869ce700b1da15c8024d08568d64004053de3cbb6300ae5c7129
Timestamp: 1720112885 Timestamp [UCT]: 2024-07-04 17:08:05 Age [y:d:h:m:s]: 01:187:17:37:36
Block: 1058483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392794 RingCT/type: yes/0
Extra: 0143667d3344de869ce700b1da15c8024d08568d64004053de3cbb6300ae5c71290211000000038fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56a2a6fe92192f1f7c35e621737b0ed5544c6a82e851f3b88d9269bd137bfcb6 0.600000000000 1528940 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": 1058493, "vin": [ { "gen": { "height": 1058483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56a2a6fe92192f1f7c35e621737b0ed5544c6a82e851f3b88d9269bd137bfcb6" } } ], "extra": [ 1, 67, 102, 125, 51, 68, 222, 134, 156, 231, 0, 177, 218, 21, 200, 2, 77, 8, 86, 141, 100, 0, 64, 83, 222, 60, 187, 99, 0, 174, 92, 113, 41, 2, 17, 0, 0, 0, 3, 143, 218, 155, 45, 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