Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e53fdb0e22eba02c457dc2d61b5105ca5aa4f2662112ae83263170807923721

Tx prefix hash: b1e7e645533a56262b6106d5ac2dc2e7ff8577f9cc305862cc8bee7252c303e9
Tx public key: ddc6be074a055ea0ffefd2ebf65afa47b81865b1c935b6f35ac23bf2e4f0728d
Timestamp: 1707074667 Timestamp [UCT]: 2024-02-04 19:24:27 Age [y:d:h:m:s]: 00:284:08:17:04
Block: 950384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203593 RingCT/type: yes/0
Extra: 01ddc6be074a055ea0ffefd2ebf65afa47b81865b1c935b6f35ac23bf2e4f0728d02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1eeb3017e52cb2b89fdd72e61be9e25e7a33f25cb2c599d50fb577e62e0f60b4 0.600000000000 1408992 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": 950394, "vin": [ { "gen": { "height": 950384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1eeb3017e52cb2b89fdd72e61be9e25e7a33f25cb2c599d50fb577e62e0f60b4" } } ], "extra": [ 1, 221, 198, 190, 7, 74, 5, 94, 160, 255, 239, 210, 235, 246, 90, 250, 71, 184, 24, 101, 177, 201, 53, 182, 243, 90, 194, 59, 242, 228, 240, 114, 141, 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