Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51d0048325a5189abc82ff2db40003d3c813cf9d0260b2931036a9ece432ad03

Tx prefix hash: 9ab950ea382101584a6a8b0964bf58d25197bc7c4f96504f5da9a98f5cf4bae1
Tx public key: 9581eadc762396e76a01b46b5f8b520dcbde75117e374e9d6c82e8028dfc04df
Timestamp: 1735296427 Timestamp [UCT]: 2024-12-27 10:47:07 Age [y:d:h:m:s]: 00:085:08:21:23
Block: 1184243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60789 RingCT/type: yes/0
Extra: 019581eadc762396e76a01b46b5f8b520dcbde75117e374e9d6c82e8028dfc04df021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c88777ecf0905c93982f39628f6fda34ba54aca2131ebc0c6fa17531ea7adff 0.600000000000 1670698 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": 1184253, "vin": [ { "gen": { "height": 1184243 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c88777ecf0905c93982f39628f6fda34ba54aca2131ebc0c6fa17531ea7adff" } } ], "extra": [ 1, 149, 129, 234, 220, 118, 35, 150, 231, 106, 1, 180, 107, 95, 139, 82, 13, 203, 222, 117, 17, 126, 55, 78, 157, 108, 130, 232, 2, 141, 252, 4, 223, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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