Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1ba409af2d5b89dc3d391994112bcd18253268f44bfbde503baa50385a0216c

Tx prefix hash: b87e5a6d876338c09f4377ee0af09ea14432e7f4d35e88e0c5b2dabec39977e6
Tx public key: cfce440f1ccc271839aef47ee9302dcf5d269e75b527a4975766ae3682b5d0b3
Timestamp: 1729359215 Timestamp [UCT]: 2024-10-19 17:33:35 Age [y:d:h:m:s]: 00:223:18:53:39
Block: 1135139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159778 RingCT/type: yes/0
Extra: 01cfce440f1ccc271839aef47ee9302dcf5d269e75b527a4975766ae3682b5d0b3021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10ee0d716862f5b3ae4c6c63a999321d7611feb3a25708e3c248189fde02af7b 0.600000000000 1618470 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": 1135149, "vin": [ { "gen": { "height": 1135139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10ee0d716862f5b3ae4c6c63a999321d7611feb3a25708e3c248189fde02af7b" } } ], "extra": [ 1, 207, 206, 68, 15, 28, 204, 39, 24, 57, 174, 244, 126, 233, 48, 45, 207, 93, 38, 158, 117, 181, 39, 164, 151, 87, 102, 174, 54, 130, 181, 208, 179, 2, 17, 0, 0, 0, 1, 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