Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 870f8f77e2758f7c36b395a6510b3a7274e89ee620a996f9b67aa90af7744c0f

Tx prefix hash: bb9518ff625aa5ac351874607d3dd7cb75ae0fe93b0c8179ff12fb3d672ada5f
Tx public key: 5f42455e811f5ae5bdcefd688ba737c93bd517368915a0ddb255a70e5787ce82
Timestamp: 1756053116 Timestamp [UCT]: 2025-08-24 16:31:56 Age [y:d:h:m:s]: 00:093:21:41:53
Block: 1353533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67054 RingCT/type: yes/0
Extra: 015f42455e811f5ae5bdcefd688ba737c93bd517368915a0ddb255a70e5787ce820211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ff04504b601b28d95e078d4daf62bbb439450aa606dc3ab0d2938259f9e4625 0.600000000000 1841508 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": 1353543, "vin": [ { "gen": { "height": 1353533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ff04504b601b28d95e078d4daf62bbb439450aa606dc3ab0d2938259f9e4625" } } ], "extra": [ 1, 95, 66, 69, 94, 129, 31, 90, 229, 189, 206, 253, 104, 139, 167, 55, 201, 59, 213, 23, 54, 137, 21, 160, 221, 178, 85, 167, 14, 87, 135, 206, 130, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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