Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfd349415a89d78c2879d6d41c8e3e69ff352cb19a0e79e7c5d8cb2b84495c6e

Tx prefix hash: 82d45d69056569a56509ba5904da5c4f9a8246c692e98166c4199609043220f4
Tx public key: e2820c5e22f02f9ac3dc9581dbd4dde096536af47bf7979a33f0fb88ee3a64d2
Timestamp: 1728861007 Timestamp [UCT]: 2024-10-13 23:10:07 Age [y:d:h:m:s]: 01:105:02:07:43
Block: 1131019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333391 RingCT/type: yes/0
Extra: 01e2820c5e22f02f9ac3dc9581dbd4dde096536af47bf7979a33f0fb88ee3a64d202110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6937e1d3ac13f1ecede26ef9443b5a745daf41469c9e06837c889cc2f01b2505 0.600000000000 1613900 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": 1131029, "vin": [ { "gen": { "height": 1131019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6937e1d3ac13f1ecede26ef9443b5a745daf41469c9e06837c889cc2f01b2505" } } ], "extra": [ 1, 226, 130, 12, 94, 34, 240, 47, 154, 195, 220, 149, 129, 219, 212, 221, 224, 150, 83, 106, 244, 123, 247, 151, 154, 51, 240, 251, 136, 238, 58, 100, 210, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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