Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16a293b034585c97bbed84e08ac2c2b52d298620b3587db9163717c3e0f1f41c

Tx prefix hash: 1edef2a0a46a1d00e7ac52b281eb11870c57d849c912e3ad4027985e705e6287
Tx public key: 3d88b9c96cf632ff64e652b87331d6a4003515d6215679d7d6a8c2fcf8f2b2ad
Timestamp: 1617089112 Timestamp [UCT]: 2021-03-30 07:25:12 Age [y:d:h:m:s]: 03:309:17:19:57
Block: 229556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 980589 RingCT/type: yes/0
Extra: 013d88b9c96cf632ff64e652b87331d6a4003515d6215679d7d6a8c2fcf8f2b2ad0211000000397071732b000000000000000000

1 output(s) for total of 106.508988683000 dcy

stealth address amount amount idx
00: 1e1ba4d95ee7b97a6df9784dc34b8f63d5f41c07c7fb84d19612cde8ea38c428 106.508988683000 476338 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": 229566, "vin": [ { "gen": { "height": 229556 } } ], "vout": [ { "amount": 106508988683, "target": { "key": "1e1ba4d95ee7b97a6df9784dc34b8f63d5f41c07c7fb84d19612cde8ea38c428" } } ], "extra": [ 1, 61, 136, 185, 201, 108, 246, 50, 255, 100, 230, 82, 184, 115, 49, 214, 164, 0, 53, 21, 214, 33, 86, 121, 215, 214, 168, 194, 252, 248, 242, 178, 173, 2, 17, 0, 0, 0, 57, 112, 113, 115, 43, 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