Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bda7bccd85196fd9a276d9dac73b640e3c06863e4c8bc29ad8991be6b1839d46

Tx prefix hash: 0d53cf66c71280cab04988441e3be5f7cb9260360264ca5f8358ffc947faf4d2
Tx public key: f25926fa3768604d30e8b02d241a326785eb3e9737a01d77a614a7aa2ac5abae
Timestamp: 1734856165 Timestamp [UCT]: 2024-12-22 08:29:25 Age [y:d:h:m:s]: 00:165:08:51:12
Block: 1180630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118016 RingCT/type: yes/0
Extra: 01f25926fa3768604d30e8b02d241a326785eb3e9737a01d77a614a7aa2ac5abae0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5be722711691c3b6b9024ee2d7a461ab3235f0db990d61b49a4aa62bea962993 0.600000000000 1667043 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": 1180640, "vin": [ { "gen": { "height": 1180630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5be722711691c3b6b9024ee2d7a461ab3235f0db990d61b49a4aa62bea962993" } } ], "extra": [ 1, 242, 89, 38, 250, 55, 104, 96, 77, 48, 232, 176, 45, 36, 26, 50, 103, 133, 235, 62, 151, 55, 160, 29, 119, 166, 20, 167, 170, 42, 197, 171, 174, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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