Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87535725f1e9f51a3527c674a43f50d54cf073addfd8a358f10075aed889b00e

Tx prefix hash: 288e84f45e7edbdc95a7c5053bd6cc38abd6f19f66a2b6e009a94650a875b72f
Tx public key: 48e31a35a8bcd7117fe93f2eb838dc10995032b9ed2f264b2655d0e079d83e17
Timestamp: 1582432642 Timestamp [UCT]: 2020-02-23 04:37:22 Age [y:d:h:m:s]: 04:327:22:29:11
Block: 70535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1127070 RingCT/type: yes/0
Extra: 0148e31a35a8bcd7117fe93f2eb838dc10995032b9ed2f264b2655d0e079d83e17021100000001c71d3ff9000000000000000000

1 output(s) for total of 358.334866271000 dcy

stealth address amount amount idx
00: 03954519290c75051495332dd95ffa891a6da0015d7c8586c0ce1d9158cb84c5 358.334866271000 130363 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": 70545, "vin": [ { "gen": { "height": 70535 } } ], "vout": [ { "amount": 358334866271, "target": { "key": "03954519290c75051495332dd95ffa891a6da0015d7c8586c0ce1d9158cb84c5" } } ], "extra": [ 1, 72, 227, 26, 53, 168, 188, 215, 17, 127, 233, 63, 46, 184, 56, 220, 16, 153, 80, 50, 185, 237, 47, 38, 75, 38, 85, 208, 224, 121, 216, 62, 23, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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