Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf346042992664c3ee900778dae26000e4f2301ca3c2e5408dd383e0027147c4

Tx prefix hash: c086a214b5f7c058a3be113032a78fdda40316cc4b1b0f370d913b8c4a15f91e
Tx public key: ab19c29d3496501ec53266b8a184363af3b3a2f20415d9aff303c6c220ddb03c
Timestamp: 1641067215 Timestamp [UCT]: 2022-01-01 20:00:15 Age [y:d:h:m:s]: 02:356:21:58:58
Block: 408375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 773254 RingCT/type: yes/0
Extra: 01ab19c29d3496501ec53266b8a184363af3b3a2f20415d9aff303c6c220ddb03c02110000000cedb0d4a3000000000000000000

1 output(s) for total of 27.219769274000 dcy

stealth address amount amount idx
00: 9d1a5c312a00982026361c9646323eec560b54c6cc97d718a7c018300b5fa4f8 27.219769274000 810388 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": 408385, "vin": [ { "gen": { "height": 408375 } } ], "vout": [ { "amount": 27219769274, "target": { "key": "9d1a5c312a00982026361c9646323eec560b54c6cc97d718a7c018300b5fa4f8" } } ], "extra": [ 1, 171, 25, 194, 157, 52, 150, 80, 30, 197, 50, 102, 184, 161, 132, 54, 58, 243, 179, 162, 242, 4, 21, 217, 175, 243, 3, 198, 194, 32, 221, 176, 60, 2, 17, 0, 0, 0, 12, 237, 176, 212, 163, 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