Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2283428b68bae1c81b845fdeb565ab6cbd3415489201f54747ac8bfc5c4c991

Tx prefix hash: 759512c79a09d7b8eae3bffa701e6b236709abc76da023443a1a0fba3eefa6cd
Tx public key: e38ac74df9e07791175b0125fcb562381f9dfda44ea7dc78b61f8f4f70850d39
Timestamp: 1676611793 Timestamp [UCT]: 2023-02-17 05:29:53 Age [y:d:h:m:s]: 01:263:17:13:38
Block: 698737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449375 RingCT/type: yes/0
Extra: 01e38ac74df9e07791175b0125fcb562381f9dfda44ea7dc78b61f8f4f70850d3902110000000e835e4d22000000000000000000

1 output(s) for total of 2.970258002000 dcy

stealth address amount amount idx
00: 580a38f55559c9a2be986127092fe92c975aff436b431852b2cecb8835518a77 2.970258002000 1142086 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": 698747, "vin": [ { "gen": { "height": 698737 } } ], "vout": [ { "amount": 2970258002, "target": { "key": "580a38f55559c9a2be986127092fe92c975aff436b431852b2cecb8835518a77" } } ], "extra": [ 1, 227, 138, 199, 77, 249, 224, 119, 145, 23, 91, 1, 37, 252, 181, 98, 56, 31, 157, 253, 164, 78, 167, 220, 120, 182, 31, 143, 79, 112, 133, 13, 57, 2, 17, 0, 0, 0, 14, 131, 94, 77, 34, 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