Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 068a929d1d634972ca6fd184a99175ceffb29ed407deb56b46d450b0342425b6

Tx prefix hash: aefaae38640f1f121b0b31c28fe302082dbdbc71c7cf3b29d1d303351317952e
Tx public key: a432a41c550b764c5804d2cbc0d7cf26999f5b79da7b8935d10151455dfb8a4d
Timestamp: 1704204204 Timestamp [UCT]: 2024-01-02 14:03:24 Age [y:d:h:m:s]: 01:106:17:42:06
Block: 926592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337408 RingCT/type: yes/0
Extra: 01a432a41c550b764c5804d2cbc0d7cf26999f5b79da7b8935d10151455dfb8a4d02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f0d0070bafc6291fa58ffce18b39fde6559da8ef858c84534a6782994758e4f 0.600000000000 1384386 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": 926602, "vin": [ { "gen": { "height": 926592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f0d0070bafc6291fa58ffce18b39fde6559da8ef858c84534a6782994758e4f" } } ], "extra": [ 1, 164, 50, 164, 28, 85, 11, 118, 76, 88, 4, 210, 203, 192, 215, 207, 38, 153, 159, 91, 121, 218, 123, 137, 53, 209, 1, 81, 69, 93, 251, 138, 77, 2, 17, 0, 0, 0, 5, 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