Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5efa4322ee2099622d892d974eead8c76b2dd8dbb8f70bc988128653afd036e0

Tx prefix hash: 2b136ba83d3162105e2ba5213449a07a8621cec877a9dc519054ea3f7fbeb164
Tx public key: a2ae3ce72b297fe0ee54d7952367981f6d194d7b7997d916dd1feb9fc81325ea
Timestamp: 1717304394 Timestamp [UCT]: 2024-06-02 04:59:54 Age [y:d:h:m:s]: 00:290:05:25:54
Block: 1035213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207427 RingCT/type: yes/0
Extra: 01a2ae3ce72b297fe0ee54d7952367981f6d194d7b7997d916dd1feb9fc81325ea02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ac978ccf1175c8df4ebf1dfa8e9250aa06162a43f2415ce2430c4b83651a444 0.600000000000 1503734 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": 1035223, "vin": [ { "gen": { "height": 1035213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ac978ccf1175c8df4ebf1dfa8e9250aa06162a43f2415ce2430c4b83651a444" } } ], "extra": [ 1, 162, 174, 60, 231, 43, 41, 127, 224, 238, 84, 215, 149, 35, 103, 152, 31, 109, 25, 77, 123, 121, 151, 217, 22, 221, 31, 235, 159, 200, 19, 37, 234, 2, 17, 0, 0, 0, 2, 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