Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44204c8fbea9c32a006d623b572ffa590f1ef455f127ea26b3c6c82977d9f5bc

Tx prefix hash: 406aa5ef7bf8d092812f2e7af0454451e9b053bf7a969c7482b2e4db9c559822
Tx public key: 6af104ce03b7ceb30218ab179b66c1d4252bdd6fb26a7d769983a808cdb9ea85
Timestamp: 1738387576 Timestamp [UCT]: 2025-02-01 05:26:16 Age [y:d:h:m:s]: 00:292:12:19:10
Block: 1209574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206815 RingCT/type: yes/0
Extra: 016af104ce03b7ceb30218ab179b66c1d4252bdd6fb26a7d769983a808cdb9ea85021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20cc4bc584db52ecb523bf70e1504246d146dee85c4e9d7ee45b77bdc4742a33 0.600000000000 1696319 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": 1209584, "vin": [ { "gen": { "height": 1209574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20cc4bc584db52ecb523bf70e1504246d146dee85c4e9d7ee45b77bdc4742a33" } } ], "extra": [ 1, 106, 241, 4, 206, 3, 183, 206, 179, 2, 24, 171, 23, 155, 102, 193, 212, 37, 43, 221, 111, 178, 106, 125, 118, 153, 131, 168, 8, 205, 185, 234, 133, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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