Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e72aa1939e7d6bb567fd20a461abeeb5cad746ffb0c8492c281813ae27a0cb46

Tx prefix hash: 78a59eb2aa607e22f77f92bc953c7e71fef318c4c921b38dba87c598ca1cb7d6
Tx public key: 6ddca245c2e76cedc7ac4dd487d54d67910c7d23e050bd447e851ce07aeade1b
Timestamp: 1740992860 Timestamp [UCT]: 2025-03-03 09:07:40 Age [y:d:h:m:s]: 00:259:05:36:58
Block: 1231135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183023 RingCT/type: yes/0
Extra: 016ddca245c2e76cedc7ac4dd487d54d67910c7d23e050bd447e851ce07aeade1b021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d370c68c2e5f2139541d8eed6e7edadd17ff24f7575633dc6ead64a4f9b2e62a 0.600000000000 1718040 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": 1231145, "vin": [ { "gen": { "height": 1231135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d370c68c2e5f2139541d8eed6e7edadd17ff24f7575633dc6ead64a4f9b2e62a" } } ], "extra": [ 1, 109, 220, 162, 69, 194, 231, 108, 237, 199, 172, 77, 212, 135, 213, 77, 103, 145, 12, 125, 35, 224, 80, 189, 68, 126, 133, 28, 224, 122, 234, 222, 27, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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