Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d00f8bfa462d35e7b84b282b522c8ac26db4bcfe60d39799ec5fc5969897e61c

Tx prefix hash: f9094eeb8509568311dd0a2eef761d129bd5571194c00e3ef77c75783590f3df
Tx public key: 0707c5acf835eac413c3965784b9e4b2bcbbe8d4d942bac6f5be9f49b3bc20d1
Timestamp: 1706179788 Timestamp [UCT]: 2024-01-25 10:49:48 Age [y:d:h:m:s]: 00:356:13:22:29
Block: 942949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255282 RingCT/type: yes/0
Extra: 010707c5acf835eac413c3965784b9e4b2bcbbe8d4d942bac6f5be9f49b3bc20d102110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32ca171a0a688df1e89ad3b0d59f8309f045fc9b9e9b21d90eed284610bdc68d 0.600000000000 1401132 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": 942959, "vin": [ { "gen": { "height": 942949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32ca171a0a688df1e89ad3b0d59f8309f045fc9b9e9b21d90eed284610bdc68d" } } ], "extra": [ 1, 7, 7, 197, 172, 248, 53, 234, 196, 19, 195, 150, 87, 132, 185, 228, 178, 188, 187, 232, 212, 217, 66, 186, 198, 245, 190, 159, 73, 179, 188, 32, 209, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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