Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adb543e7a504ac9dcd3160930599eef22e2c5be4dfb23b858a804531f91a634e

Tx prefix hash: 49af43d4a73f7a856bec20335ceff7f3eb43bc187551d2789e2c664e919dbeb3
Tx public key: 3b58bdb92c3fb35a48ebd7f450237bd5e473ae575552a0ba1130e7e8c94cb9e8
Timestamp: 1699760267 Timestamp [UCT]: 2023-11-12 03:37:47 Age [y:d:h:m:s]: 01:070:18:49:43
Block: 889757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311953 RingCT/type: yes/0
Extra: 013b58bdb92c3fb35a48ebd7f450237bd5e473ae575552a0ba1130e7e8c94cb9e8021100000004faf35c9c000000000000000000

1 output(s) for total of 0.691617067000 dcy

stealth address amount amount idx
00: b80e4f4fae401337ab0991fdbf97896105a4384b083d82c479f18fc82723bcf0 0.691617067000 1345770 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": 889767, "vin": [ { "gen": { "height": 889757 } } ], "vout": [ { "amount": 691617067, "target": { "key": "b80e4f4fae401337ab0991fdbf97896105a4384b083d82c479f18fc82723bcf0" } } ], "extra": [ 1, 59, 88, 189, 185, 44, 63, 179, 90, 72, 235, 215, 244, 80, 35, 123, 213, 228, 115, 174, 87, 85, 82, 160, 186, 17, 48, 231, 232, 201, 76, 185, 232, 2, 17, 0, 0, 0, 4, 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