Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 651d9175bd200f8905fc49df8c966e6317575eb638c13ec8daf107fd7a34417d

Tx prefix hash: 1839a5eb1122fabf39a46c2ff933ee2a7e6ec86923c4455b376c830ad115eb22
Tx public key: 8e1391043d47ee1416d940cf548e4e468ec9f93257a3f7f6ead81e9653b47a45
Timestamp: 1749407276 Timestamp [UCT]: 2025-06-08 18:27:56 Age [y:d:h:m:s]: 00:164:12:22:58
Block: 1300810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115256 RingCT/type: yes/0
Extra: 018e1391043d47ee1416d940cf548e4e468ec9f93257a3f7f6ead81e9653b47a45021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 058c3c2c61339f15aa95ad0d1763e4d41f91653b3b9a1f3cda601ddb217a4156 0.600000000000 1788361 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": 1300820, "vin": [ { "gen": { "height": 1300810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "058c3c2c61339f15aa95ad0d1763e4d41f91653b3b9a1f3cda601ddb217a4156" } } ], "extra": [ 1, 142, 19, 145, 4, 61, 71, 238, 20, 22, 217, 64, 207, 84, 142, 78, 70, 142, 201, 249, 50, 87, 163, 247, 246, 234, 216, 30, 150, 83, 180, 122, 69, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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