Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6e78a0d100d4ba27b3591fc2b707621bbf8fde193520a7bf9e8828dd0295ab4

Tx prefix hash: 40c412205d53c44625c8f9499bd9e074119b2262d00583ebeb7f98eeed6c68f5
Tx public key: 9d1528e19b5932556615551f9c73f29df273ee42f4ef73b212c3cd13d9f5db31
Timestamp: 1702881903 Timestamp [UCT]: 2023-12-18 06:45:03 Age [y:d:h:m:s]: 01:178:22:29:40
Block: 915640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388978 RingCT/type: yes/0
Extra: 019d1528e19b5932556615551f9c73f29df273ee42f4ef73b212c3cd13d9f5db3102110000000efaf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eebe41af7d7d4136374b8c25b697851afa230daae68c8ee99a41f5fbb7b443e9 0.600000000000 1373036 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": 915650, "vin": [ { "gen": { "height": 915640 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eebe41af7d7d4136374b8c25b697851afa230daae68c8ee99a41f5fbb7b443e9" } } ], "extra": [ 1, 157, 21, 40, 225, 155, 89, 50, 85, 102, 21, 85, 31, 156, 115, 242, 157, 242, 115, 238, 66, 244, 239, 115, 178, 18, 195, 205, 19, 217, 245, 219, 49, 2, 17, 0, 0, 0, 14, 250, 243, 92, 156, 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