Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91f7ee7edc640d78c3bfbc9dea1ad6450fbd1f0c730973b085e05cf2c41571d5

Tx prefix hash: f7604eb2eb5c4a08485043224568f5aa4681278e19a7698109ef91c15c0cb316
Tx public key: 1bb7a9ecd60e86cd5e0f11333e0ef6d1a92f2b579633bdb42b91378ccd25fd39
Timestamp: 1762373069 Timestamp [UCT]: 2025-11-05 20:04:29 Age [y:d:h:m:s]: 00:061:00:59:22
Block: 1405717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43731 RingCT/type: yes/0
Extra: 011bb7a9ecd60e86cd5e0f11333e0ef6d1a92f2b579633bdb42b91378ccd25fd390211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 262ec5ac9dc946960bdc7d278a1ad85dd387066c0a84f7a7ad3d10a284cff0bc 0.600000000000 1894098 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": 1405727, "vin": [ { "gen": { "height": 1405717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "262ec5ac9dc946960bdc7d278a1ad85dd387066c0a84f7a7ad3d10a284cff0bc" } } ], "extra": [ 1, 27, 183, 169, 236, 214, 14, 134, 205, 94, 15, 17, 51, 62, 14, 246, 209, 169, 47, 43, 87, 150, 51, 189, 180, 43, 145, 55, 140, 205, 37, 253, 57, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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