Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 079ef832375b6bd0bb565782ce86f0edcf57629a324775215be97385adc33a66

Tx prefix hash: 81c172b53435ac8a722cb45d36cab0a3de5b81d3661a62b6a7c2418afb6033d3
Tx public key: e6d44ae61296d99de5511271227d7321c9d3b7b611bc2c1ebe0631c5d846ad9a
Timestamp: 1730578619 Timestamp [UCT]: 2024-11-02 20:16:59 Age [y:d:h:m:s]: 00:062:13:57:42
Block: 1145172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44789 RingCT/type: yes/0
Extra: 01e6d44ae61296d99de5511271227d7321c9d3b7b611bc2c1ebe0631c5d846ad9a0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57da80e1cbc75f09c69be5c6d6a40f3f099516de2984bcd5134fc78d74d2fdfa 0.600000000000 1629569 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": 1145182, "vin": [ { "gen": { "height": 1145172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57da80e1cbc75f09c69be5c6d6a40f3f099516de2984bcd5134fc78d74d2fdfa" } } ], "extra": [ 1, 230, 212, 74, 230, 18, 150, 217, 157, 229, 81, 18, 113, 34, 125, 115, 33, 201, 211, 183, 182, 17, 188, 44, 30, 190, 6, 49, 197, 216, 70, 173, 154, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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