Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 004a66926ac72489d680d513632e1c6352ae1231d42c792c9f033a3cf4f7aca6

Tx prefix hash: d31fc2e5da14d53c7f3f380c7fddbc9dcf9490422c86771f940e504dfb720622
Tx public key: d2e5d86fcfb1bbe1ee05f52505112df4ba6b9e56e44ef1921e09c49b25d5cac4
Timestamp: 1723666158 Timestamp [UCT]: 2024-08-14 20:09:18 Age [y:d:h:m:s]: 00:271:07:41:50
Block: 1087947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193810 RingCT/type: yes/0
Extra: 01d2e5d86fcfb1bbe1ee05f52505112df4ba6b9e56e44ef1921e09c49b25d5cac402110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: feeab9b8319da4271b19ef2c304340ec5526dee6ba1f1867d222ae99ca736626 0.600000000000 1562558 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": 1087957, "vin": [ { "gen": { "height": 1087947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "feeab9b8319da4271b19ef2c304340ec5526dee6ba1f1867d222ae99ca736626" } } ], "extra": [ 1, 210, 229, 216, 111, 207, 177, 187, 225, 238, 5, 245, 37, 5, 17, 45, 244, 186, 107, 158, 86, 228, 78, 241, 146, 30, 9, 196, 155, 37, 213, 202, 196, 2, 17, 0, 0, 0, 4, 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