Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a8050926eaf3b626ddd011a3240d5132f6f868e1a307c44f7c51e5c330b5d10

Tx prefix hash: 28fe5c768e672137b1172e4ff87f22fe15fc79974303a621a27907d6527f28e9
Tx public key: 30eeb828e86c3ad7785ad46444ea6e9e1941a6a70dc707164bd16ed7d06d44e5
Timestamp: 1588514006 Timestamp [UCT]: 2020-05-03 13:53:26 Age [y:d:h:m:s]: 04:207:21:40:36
Block: 97916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1064172 RingCT/type: yes/0
Extra: 0130eeb828e86c3ad7785ad46444ea6e9e1941a6a70dc707164bd16ed7d06d44e50211000001c46fa03929000000000000000000

1 output(s) for total of 290.779918236000 dcy

stealth address amount amount idx
00: 6503f0fe739096c68fab7f036eb60157c5d3da75ef8bfee052c293dc93c06a23 290.779918236000 173243 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": 97926, "vin": [ { "gen": { "height": 97916 } } ], "vout": [ { "amount": 290779918236, "target": { "key": "6503f0fe739096c68fab7f036eb60157c5d3da75ef8bfee052c293dc93c06a23" } } ], "extra": [ 1, 48, 238, 184, 40, 232, 108, 58, 215, 120, 90, 212, 100, 68, 234, 110, 158, 25, 65, 166, 167, 13, 199, 7, 22, 75, 209, 110, 215, 208, 109, 68, 229, 2, 17, 0, 0, 1, 196, 111, 160, 57, 41, 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