Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70b5c861a40f55676202bde5b23f118cd27141a01b5baa01c0b9a706ae08fb52

Tx prefix hash: 44cdcaa380cfb68627e80eaaec0f51f12994382e398a12d6eb28519a5f96c04f
Tx public key: ee9ec22e90159be91a967bd1b32a2503f91817c46804c5c1990eff946eaac6cf
Timestamp: 1635570317 Timestamp [UCT]: 2021-10-30 05:05:17 Age [y:d:h:m:s]: 04:054:20:56:00
Block: 363420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1076134 RingCT/type: yes/0
Extra: 01ee9ec22e90159be91a967bd1b32a2503f91817c46804c5c1990eff946eaac6cf02110000003a6a2c97e6000000000000000000

1 output(s) for total of 38.357179700000 dcy

stealth address amount amount idx
00: 502b5c0d9ffeeddc777f6e3b8fac07c8632781c70fa4e51c03dd096d6bfe05b0 38.357179700000 738632 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": 363430, "vin": [ { "gen": { "height": 363420 } } ], "vout": [ { "amount": 38357179700, "target": { "key": "502b5c0d9ffeeddc777f6e3b8fac07c8632781c70fa4e51c03dd096d6bfe05b0" } } ], "extra": [ 1, 238, 158, 194, 46, 144, 21, 155, 233, 26, 150, 123, 209, 179, 42, 37, 3, 249, 24, 23, 196, 104, 4, 197, 193, 153, 14, 255, 148, 110, 170, 198, 207, 2, 17, 0, 0, 0, 58, 106, 44, 151, 230, 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