Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef60c1a0b4058b5153f37d980b65893906113397c1749de3061e7eac8c9879ac

Tx prefix hash: d241a4c239f2d2fae78b8ca2c22d3ae192c4a2bce62a477af4edbe1cfcba2925
Tx public key: d69dc0226e6ffb1717316f84622c46e01bcef42f75eac195e5ed3ac5434d6c1c
Timestamp: 1765036648 Timestamp [UCT]: 2025-12-06 15:57:28 Age [y:d:h:m:s]: 00:017:00:25:43
Block: 1427799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12172 RingCT/type: yes/0
Extra: 01d69dc0226e6ffb1717316f84622c46e01bcef42f75eac195e5ed3ac5434d6c1c02110000000270609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d266bb1f67565fd946e67e5c63c1e02621bfbfadf483df2de7f259ac0244c1a 0.600000000000 1916506 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": 1427809, "vin": [ { "gen": { "height": 1427799 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d266bb1f67565fd946e67e5c63c1e02621bfbfadf483df2de7f259ac0244c1a" } } ], "extra": [ 1, 214, 157, 192, 34, 110, 111, 251, 23, 23, 49, 111, 132, 98, 44, 70, 224, 27, 206, 244, 47, 117, 234, 193, 149, 229, 237, 58, 197, 67, 77, 108, 28, 2, 17, 0, 0, 0, 2, 112, 96, 157, 3, 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