Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17ef5b87ba9fa48999c56f9c9f388bcb839f2cfeb515cdf406d10cf1d56ff6c4

Tx prefix hash: 56a0fa6d5998a002916a1c94cbbc55fc6f1649ab643fc6510bf0e5e1ae420218
Tx public key: 6aebb07eebbe8b1d9465eae75adf60bb4fce162401724cec0957101f454f0fb8
Timestamp: 1658725684 Timestamp [UCT]: 2022-07-25 05:08:04 Age [y:d:h:m:s]: 02:243:09:17:15
Block: 551169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 695147 RingCT/type: yes/0
Extra: 016aebb07eebbe8b1d9465eae75adf60bb4fce162401724cec0957101f454f0fb8021100000002ea8cbb85000000000000000000

1 output(s) for total of 9.156899178000 dcy

stealth address amount amount idx
00: 7472df5a9672d54f1671c387d5b47d866564fecaaa54cde8e09931c3be17d70d 9.156899178000 982735 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": 551179, "vin": [ { "gen": { "height": 551169 } } ], "vout": [ { "amount": 9156899178, "target": { "key": "7472df5a9672d54f1671c387d5b47d866564fecaaa54cde8e09931c3be17d70d" } } ], "extra": [ 1, 106, 235, 176, 126, 235, 190, 139, 29, 148, 101, 234, 231, 90, 223, 96, 187, 79, 206, 22, 36, 1, 114, 76, 236, 9, 87, 16, 31, 69, 79, 15, 184, 2, 17, 0, 0, 0, 2, 234, 140, 187, 133, 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