Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d77d594b7f1c694ef2a5abbac6732acb9f5a8f5dc5dd89462b174ef671e5ab4

Tx prefix hash: fc5f9a7957261cd2413e4074716fbe389d1f59c9e2481be12023113ae73b5351
Tx public key: 0c9fa5f1dee0afed3cccf46928e5bcd663c3341e180dbcde7205be6e425a3fdf
Timestamp: 1706480936 Timestamp [UCT]: 2024-01-28 22:28:56 Age [y:d:h:m:s]: 01:140:05:54:06
Block: 945453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361250 RingCT/type: yes/0
Extra: 010c9fa5f1dee0afed3cccf46928e5bcd663c3341e180dbcde7205be6e425a3fdf0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c7588bee25cd613d2c10a92e9d8db61c01dc2915eb8ad64bbe935f339723a66 0.600000000000 1403767 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": 945463, "vin": [ { "gen": { "height": 945453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c7588bee25cd613d2c10a92e9d8db61c01dc2915eb8ad64bbe935f339723a66" } } ], "extra": [ 1, 12, 159, 165, 241, 222, 224, 175, 237, 60, 204, 244, 105, 40, 229, 188, 214, 99, 195, 52, 30, 24, 13, 188, 222, 114, 5, 190, 110, 66, 90, 63, 223, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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