Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a357d367a47b572be43c6ea59670507ee8b3f9e56a10dc4ee5aa605e82bcae0

Tx prefix hash: 90714e1a7695215d1eecb99e1ac433aa663e4d4460f684776838aafab10c8de2
Tx public key: 0cbc887226d7a18d390e43617451540afb89378d1fb5b0ef92cf119a2bec2a12
Timestamp: 1736830820 Timestamp [UCT]: 2025-01-14 05:00:20 Age [y:d:h:m:s]: 00:155:13:21:01
Block: 1196950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110871 RingCT/type: yes/0
Extra: 010cbc887226d7a18d390e43617451540afb89378d1fb5b0ef92cf119a2bec2a120211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a0c3843d3dbfb9cad1fb4ea1deab7f28c7410943be1ca926f0cbfc44525d108 0.600000000000 1683555 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": 1196960, "vin": [ { "gen": { "height": 1196950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a0c3843d3dbfb9cad1fb4ea1deab7f28c7410943be1ca926f0cbfc44525d108" } } ], "extra": [ 1, 12, 188, 136, 114, 38, 215, 161, 141, 57, 14, 67, 97, 116, 81, 84, 10, 251, 137, 55, 141, 31, 181, 176, 239, 146, 207, 17, 154, 43, 236, 42, 18, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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