Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe71b93786a8771a1ccc0d1fb4bb452ebbc2d2d94734ca18a23b177a746de39e

Tx prefix hash: d66887c62f796a46ca6cff83e190999aeca3c8fb9e6efff5bfbffa6a86b099b4
Tx public key: c3a8696cfa58a57cd92f8e090fde1d7bf834edf7a881b03d6543a338de871da1
Timestamp: 1582896697 Timestamp [UCT]: 2020-02-28 13:31:37 Age [y:d:h:m:s]: 04:347:10:50:00
Block: 73415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1141730 RingCT/type: yes/0
Extra: 01c3a8696cfa58a57cd92f8e090fde1d7bf834edf7a881b03d6543a338de871da102110000000d4ac5aa02000000000000000000

1 output(s) for total of 350.553200309000 dcy

stealth address amount amount idx
00: 1d66c4ae92f5c4e9d7918b2693f56590440910f29aacdbb10997fd59731e8bbb 350.553200309000 135428 of 0

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": 73425, "vin": [ { "gen": { "height": 73415 } } ], "vout": [ { "amount": 350553200309, "target": { "key": "1d66c4ae92f5c4e9d7918b2693f56590440910f29aacdbb10997fd59731e8bbb" } } ], "extra": [ 1, 195, 168, 105, 108, 250, 88, 165, 124, 217, 47, 142, 9, 15, 222, 29, 123, 248, 52, 237, 247, 168, 129, 176, 61, 101, 67, 163, 56, 222, 135, 29, 161, 2, 17, 0, 0, 0, 13, 74, 197, 170, 2, 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