Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d80e825cc04a04682b611afbe6d4c73d4fc7ab17d490c3ca8097e1f8513a1af

Tx prefix hash: f968eb66ffd92c6e4e1ff385bc4fcc22a1dd4970f5394fe7762f9189c8fd5fa0
Tx public key: cf0f4d58aefe0abf23e4f021d8b744832df9570f7b83bdd52afe461fd0c58be6
Timestamp: 1705447500 Timestamp [UCT]: 2024-01-16 23:25:00 Age [y:d:h:m:s]: 01:297:20:22:11
Block: 936876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471712 RingCT/type: yes/0
Extra: 01cf0f4d58aefe0abf23e4f021d8b744832df9570f7b83bdd52afe461fd0c58be60211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1573db676d3a2ff9798937e1d6e89377c49f3b26cbd3dda1b1c21d37dd92c360 0.600000000000 1394918 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": 936886, "vin": [ { "gen": { "height": 936876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1573db676d3a2ff9798937e1d6e89377c49f3b26cbd3dda1b1c21d37dd92c360" } } ], "extra": [ 1, 207, 15, 77, 88, 174, 254, 10, 191, 35, 228, 240, 33, 216, 183, 68, 131, 45, 249, 87, 15, 123, 131, 189, 213, 42, 254, 70, 31, 208, 197, 139, 230, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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