Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 904b4158a803692a5d376e0c68b979a114240ef4226340b6ecc7adbe02c805ec

Tx prefix hash: cdc782345263cfc385a206e082ef851d63ab7e9f84dd88c932b9338103de420b
Tx public key: 21ef146f1fc4c79fcc535b7281a23b75ae1049b6d931e8574172a90c3cecae53
Timestamp: 1725656379 Timestamp [UCT]: 2024-09-06 20:59:39 Age [y:d:h:m:s]: 00:190:02:24:08
Block: 1104450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135725 RingCT/type: yes/0
Extra: 0121ef146f1fc4c79fcc535b7281a23b75ae1049b6d931e8574172a90c3cecae53021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f72e67c1986e56ea8bdf51b732520ca8a716cd1f5a55c7f606b5aedfb839e6f 0.600000000000 1581595 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": 1104460, "vin": [ { "gen": { "height": 1104450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f72e67c1986e56ea8bdf51b732520ca8a716cd1f5a55c7f606b5aedfb839e6f" } } ], "extra": [ 1, 33, 239, 20, 111, 31, 196, 199, 159, 204, 83, 91, 114, 129, 162, 59, 117, 174, 16, 73, 182, 217, 49, 232, 87, 65, 114, 169, 12, 60, 236, 174, 83, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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