Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1453a5b4a47ba4f873f571f14133efd670e0b66f31b3b0079a4dbd6c101769a3

Tx prefix hash: 4f6c4b2554efdcd52fae070e4d404f5e760c94e533e9790d972e256c5972f3fe
Tx public key: b813ef9415c7f4aecbad59201c65963961f0dfc11d5403257313df4ecbb7a64d
Timestamp: 1712525505 Timestamp [UCT]: 2024-04-07 21:31:45 Age [y:d:h:m:s]: 00:234:23:02:16
Block: 995556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168239 RingCT/type: yes/0
Extra: 01b813ef9415c7f4aecbad59201c65963961f0dfc11d5403257313df4ecbb7a64d02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d75a4a40381e41a0198041ad0da63f7eb76ce8b8730575cc387c931e87e7d6bf 0.600000000000 1455966 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": 995566, "vin": [ { "gen": { "height": 995556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d75a4a40381e41a0198041ad0da63f7eb76ce8b8730575cc387c931e87e7d6bf" } } ], "extra": [ 1, 184, 19, 239, 148, 21, 199, 244, 174, 203, 173, 89, 32, 28, 101, 150, 57, 97, 240, 223, 193, 29, 84, 3, 37, 115, 19, 223, 78, 203, 183, 166, 77, 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