Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a49c8e3aa8fe9b7bf2223c2628f0b210a3447043796fc932ad5144d4640f5c3d

Tx prefix hash: 1c9a6e5fb38da41e0a605ee7f3322509c285b5dd09fc7ddc846f55ab58ed6432
Tx public key: 3c46bf76e604963fe86dfe4c38a72db1c01cbc504186fbdd7e86b4c6cd741ccb
Timestamp: 1580714863 Timestamp [UCT]: 2020-02-03 07:27:43 Age [y:d:h:m:s]: 05:040:12:45:52
Block: 57816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1180823 RingCT/type: yes/0
Extra: 013c46bf76e604963fe86dfe4c38a72db1c01cbc504186fbdd7e86b4c6cd741ccb021100000003d81c26c0000000000000000000

1 output(s) for total of 394.858816040000 dcy

stealth address amount amount idx
00: 2a9fb00a856b5f98b7d9bb102d7c43ab9c995cdcaf7dd83b1a009f4192924770 394.858816040000 106879 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": 57826, "vin": [ { "gen": { "height": 57816 } } ], "vout": [ { "amount": 394858816040, "target": { "key": "2a9fb00a856b5f98b7d9bb102d7c43ab9c995cdcaf7dd83b1a009f4192924770" } } ], "extra": [ 1, 60, 70, 191, 118, 230, 4, 150, 63, 232, 109, 254, 76, 56, 167, 45, 177, 192, 28, 188, 80, 65, 134, 251, 221, 126, 134, 180, 198, 205, 116, 28, 203, 2, 17, 0, 0, 0, 3, 216, 28, 38, 192, 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