Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbb2d06c7ed00ee69f19e59472ca7adde0b19bbf3655894ab323a2d6b0f4b327

Tx prefix hash: 8e0f8dc98a190053485519a16059ebfcaf64ecd534f23f805aa07e1446245737
Tx public key: 2cb88ecb0a66f07db819adc70422f69f1a63d9163149133aa41edba3b9e54cd1
Timestamp: 1727627185 Timestamp [UCT]: 2024-09-29 16:26:25 Age [y:d:h:m:s]: 01:001:03:09:42
Block: 1120789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259133 RingCT/type: yes/0
Extra: 012cb88ecb0a66f07db819adc70422f69f1a63d9163149133aa41edba3b9e54cd1021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a15a075601a876fe6bd5ccb30b634b9a183a63437f3720f13e02d2204b85d2ec 0.600000000000 1602830 of 15

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": 1120799, "vin": [ { "gen": { "height": 1120789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a15a075601a876fe6bd5ccb30b634b9a183a63437f3720f13e02d2204b85d2ec" } } ], "extra": [ 1, 44, 184, 142, 203, 10, 102, 240, 125, 184, 25, 173, 199, 4, 34, 246, 159, 26, 99, 217, 22, 49, 73, 19, 58, 164, 30, 219, 163, 185, 229, 76, 209, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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