Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b566ab1e6dec5e194c0e84f3bf47bc3cc5c78a12d7bc6b489be89e0cf1c6c1ea

Tx prefix hash: a258a8607f91e824ff0bf8bdd710f0d20586950b7b8e9daf2b273d340aabb0bf
Tx public key: 1bf7db5db025898c3bbe20bd6dc4bb70485bf45a23e6c36e01e61fc03ae13e63
Timestamp: 1705391543 Timestamp [UCT]: 2024-01-16 07:52:23 Age [y:d:h:m:s]: 01:300:10:16:19
Block: 936417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 473550 RingCT/type: yes/0
Extra: 011bf7db5db025898c3bbe20bd6dc4bb70485bf45a23e6c36e01e61fc03ae13e6302110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03f894e735dbb6ee3ef45339545cedc218637949a04eca69baa7c550a94c5c14 0.600000000000 1394443 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": 936427, "vin": [ { "gen": { "height": 936417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03f894e735dbb6ee3ef45339545cedc218637949a04eca69baa7c550a94c5c14" } } ], "extra": [ 1, 27, 247, 219, 93, 176, 37, 137, 140, 59, 190, 32, 189, 109, 196, 187, 112, 72, 91, 244, 90, 35, 230, 195, 110, 1, 230, 31, 192, 58, 225, 62, 99, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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