Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 196578ec013fa3e017ca85497cf162a705bf841fd558e0cfeadfe17b044b912b

Tx prefix hash: c8bb19cf622b27cc91e4fdb4d7bb22c6fad48c9e040abc0d75799a531c95de09
Tx public key: f848cb43fb7edae403b9ffefdcd6291fafb9c53b79b821a4d45703c405543551
Timestamp: 1733391249 Timestamp [UCT]: 2024-12-05 09:34:09 Age [y:d:h:m:s]: 00:134:00:43:15
Block: 1168480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95595 RingCT/type: yes/0
Extra: 01f848cb43fb7edae403b9ffefdcd6291fafb9c53b79b821a4d45703c405543551021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 129ed066e6ad2d6560b5c30e1cc9bba17f474df94eb430dbcafd3c346de3b88d 0.600000000000 1654189 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": 1168490, "vin": [ { "gen": { "height": 1168480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "129ed066e6ad2d6560b5c30e1cc9bba17f474df94eb430dbcafd3c346de3b88d" } } ], "extra": [ 1, 248, 72, 203, 67, 251, 126, 218, 228, 3, 185, 255, 239, 220, 214, 41, 31, 175, 185, 197, 59, 121, 184, 33, 164, 212, 87, 3, 196, 5, 84, 53, 81, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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