Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d6b81ed995c5c4813b243bd10c049c1ab64088297fbfa95cc0fbb764c9e75d2

Tx prefix hash: 7b2a4e673149f00506aeb1799a93659643c2bfa1244b1e52271841073f859818
Tx public key: 811c3e4131f230b106408da9f0e86ec85f4c6f341fdfc4458e5305477b87d9dd
Timestamp: 1745289539 Timestamp [UCT]: 2025-04-22 02:38:59 Age [y:d:h:m:s]: 00:023:00:52:53
Block: 1266699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16483 RingCT/type: yes/0
Extra: 01811c3e4131f230b106408da9f0e86ec85f4c6f341fdfc4458e5305477b87d9dd021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddf2a7348758ecb0f583bbfc6af0711de4b02f3331f68fa7b0e36eef9b1b7b5a 0.600000000000 1753920 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": 1266709, "vin": [ { "gen": { "height": 1266699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddf2a7348758ecb0f583bbfc6af0711de4b02f3331f68fa7b0e36eef9b1b7b5a" } } ], "extra": [ 1, 129, 28, 62, 65, 49, 242, 48, 177, 6, 64, 141, 169, 240, 232, 110, 200, 95, 76, 111, 52, 31, 223, 196, 69, 142, 83, 5, 71, 123, 135, 217, 221, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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