Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 343bea295de39ec3f8672128c8fb0195fd6a8a5e462064802457d6eaec002473

Tx prefix hash: fc4af98de8a9e901602633bcc674b862ce51d42b8f04abeef8883f3e55dc6630
Tx public key: 229e5a6060b83a02cd55d42110f04b3d37830e2982217bce3430c12bd4ea560a
Timestamp: 1725900130 Timestamp [UCT]: 2024-09-09 16:42:10 Age [y:d:h:m:s]: 00:200:16:45:20
Block: 1106474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143268 RingCT/type: yes/0
Extra: 01229e5a6060b83a02cd55d42110f04b3d37830e2982217bce3430c12bd4ea560a02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6fd046975f6f7f915cda78f3ddf2c67c48a191b0a7e88c154c7f19695d6368a 0.600000000000 1584073 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": 1106484, "vin": [ { "gen": { "height": 1106474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6fd046975f6f7f915cda78f3ddf2c67c48a191b0a7e88c154c7f19695d6368a" } } ], "extra": [ 1, 34, 158, 90, 96, 96, 184, 58, 2, 205, 85, 212, 33, 16, 240, 75, 61, 55, 131, 14, 41, 130, 33, 123, 206, 52, 48, 193, 43, 212, 234, 86, 10, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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