Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0603e78df75014a99a51fb9d8e10f22f5bd29513e89ea87c19ed899d7fb4b0db

Tx prefix hash: 4cd55956ad6a99b41f4222a0a0fac6190f6b746cc13e44799a1befaef63acbfc
Tx public key: e30682f2ac8990114068bf0ee5c89d69ea2aad7c6a68f38bae09adcdbda02b44
Timestamp: 1580409752 Timestamp [UCT]: 2020-01-30 18:42:32 Age [y:d:h:m:s]: 04:301:09:31:20
Block: 55614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106260 RingCT/type: yes/0
Extra: 01e30682f2ac8990114068bf0ee5c89d69ea2aad7c6a68f38bae09adcdbda02b440211000000144943cd9f000000000000000000

1 output(s) for total of 401.539761118000 dcy

stealth address amount amount idx
00: 6be3aca370c538427302156fbb005973fdd9a5d5ecc0a0df9515ea189697ff24 401.539761118000 102628 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": 55624, "vin": [ { "gen": { "height": 55614 } } ], "vout": [ { "amount": 401539761118, "target": { "key": "6be3aca370c538427302156fbb005973fdd9a5d5ecc0a0df9515ea189697ff24" } } ], "extra": [ 1, 227, 6, 130, 242, 172, 137, 144, 17, 64, 104, 191, 14, 229, 200, 157, 105, 234, 42, 173, 124, 106, 104, 243, 139, 174, 9, 173, 205, 189, 160, 43, 68, 2, 17, 0, 0, 0, 20, 73, 67, 205, 159, 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