Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cc4afb0af9565082ff2c8aa457623ae495b775c2a0e955c3afc2479b1548140

Tx prefix hash: fb42b61091b522706c47cc8392a299a80031673a365874d3919bfddf6d3d40db
Tx public key: 10d5dedf8d085e27aa921e3a427e5cd93e74885d897037d27c86d7d52769cc2f
Timestamp: 1721405011 Timestamp [UCT]: 2024-07-19 16:03:31 Age [y:d:h:m:s]: 00:251:09:33:19
Block: 1069217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179575 RingCT/type: yes/0
Extra: 0110d5dedf8d085e27aa921e3a427e5cd93e74885d897037d27c86d7d52769cc2f021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74fde8f124161c0c431ad2023432d1e13346ca8483ce4dece3650e36f00d26d0 0.600000000000 1540556 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": 1069227, "vin": [ { "gen": { "height": 1069217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74fde8f124161c0c431ad2023432d1e13346ca8483ce4dece3650e36f00d26d0" } } ], "extra": [ 1, 16, 213, 222, 223, 141, 8, 94, 39, 170, 146, 30, 58, 66, 126, 92, 217, 62, 116, 136, 93, 137, 112, 55, 210, 124, 134, 215, 213, 39, 105, 204, 47, 2, 17, 0, 0, 0, 8, 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