Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e36727c3c8c4c11a11331cb3236f730bf6eb5ef8277d79a0015984f76e44daad

Tx prefix hash: ca0da254fc6d285c348dc3428863df17b5f5edb0375719e40eef7fdb125b9027
Tx public key: bc2a32fba6fef0cf3d482947657ecc37ded7fb10d8d24d05bb2d362ca93130da
Timestamp: 1716565175 Timestamp [UCT]: 2024-05-24 15:39:35 Age [y:d:h:m:s]: 00:299:14:45:39
Block: 1029082 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214152 RingCT/type: yes/0
Extra: 01bc2a32fba6fef0cf3d482947657ecc37ded7fb10d8d24d05bb2d362ca93130da02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1df1e62a21e0d5b0a3a32cb4e88b8177f5a75350bf4151d4befcf3088eb46af 0.600000000000 1497085 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": 1029092, "vin": [ { "gen": { "height": 1029082 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1df1e62a21e0d5b0a3a32cb4e88b8177f5a75350bf4151d4befcf3088eb46af" } } ], "extra": [ 1, 188, 42, 50, 251, 166, 254, 240, 207, 61, 72, 41, 71, 101, 126, 204, 55, 222, 215, 251, 16, 216, 210, 77, 5, 187, 45, 54, 44, 169, 49, 48, 218, 2, 17, 0, 0, 0, 1, 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