Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d57c5ac989adb62419460d9e26bfff9e5cb3035c6b979d54a8f340d96da75e0

Tx prefix hash: 37872c4c2cf520076c54563752904bef69e88851bb7e377766f2f54a0dd72c58
Tx public key: 0acbd5114c75799647e5639bbfa92ea3f5888b1f83c8af6353311e8e5990bca1
Timestamp: 1734579371 Timestamp [UCT]: 2024-12-19 03:36:11 Age [y:d:h:m:s]: 00:020:22:23:43
Block: 1178341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14942 RingCT/type: yes/0
Extra: 010acbd5114c75799647e5639bbfa92ea3f5888b1f83c8af6353311e8e5990bca1021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5749e0a9f55bff6a4ea57873781c325b18e5f1696e7a078df0b1dd5b6e1b5da3 0.600000000000 1664728 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": 1178351, "vin": [ { "gen": { "height": 1178341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5749e0a9f55bff6a4ea57873781c325b18e5f1696e7a078df0b1dd5b6e1b5da3" } } ], "extra": [ 1, 10, 203, 213, 17, 76, 117, 121, 150, 71, 229, 99, 155, 191, 169, 46, 163, 245, 136, 139, 31, 131, 200, 175, 99, 83, 49, 30, 142, 89, 144, 188, 161, 2, 17, 0, 0, 0, 4, 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