Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cdba9f0a40a30b3a7ff519b45ff41c7fe46888864b7b14e1f2f7c6bdceae186

Tx prefix hash: b32addbd79ade6ba737b8aa57dbc0f6168c5260d3af7006f809d5e5634bc15f3
Tx public key: 1ab256979a9d6921fa58f2859b9df952a8427a527065ab9ec7f62ccd506269e9
Timestamp: 1730037991 Timestamp [UCT]: 2024-10-27 14:06:31 Age [y:d:h:m:s]: 00:027:23:43:53
Block: 1140734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19995 RingCT/type: yes/0
Extra: 011ab256979a9d6921fa58f2859b9df952a8427a527065ab9ec7f62ccd506269e9021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a919ba33870526341fce05e0616de91fd54b4e2b23ba1c8e2de338fa080abfde 0.600000000000 1624537 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": 1140744, "vin": [ { "gen": { "height": 1140734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a919ba33870526341fce05e0616de91fd54b4e2b23ba1c8e2de338fa080abfde" } } ], "extra": [ 1, 26, 178, 86, 151, 154, 157, 105, 33, 250, 88, 242, 133, 155, 157, 249, 82, 168, 66, 122, 82, 112, 101, 171, 158, 199, 246, 44, 205, 80, 98, 105, 233, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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