Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08e214e4cbd89f4b75677393f45ba055df236006110f6a11447f519898c52b7a

Tx prefix hash: 17970a87df1a4bb3be24e7a1c78371fa78df445161e01a8fd15e37e59429b8e8
Tx public key: 89bfd98a92b5b7e7c1f85401df0f8342528dd6a8097422dce639d8d214ba29ee
Timestamp: 1751536855 Timestamp [UCT]: 2025-07-03 10:00:55 Age [y:d:h:m:s]: 00:141:05:03:48
Block: 1317860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99160 RingCT/type: yes/0
Extra: 0189bfd98a92b5b7e7c1f85401df0f8342528dd6a8097422dce639d8d214ba29ee02110000000c43846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74925ba3189366220a7559b0ccb5eaa69d3cd3ad0aa6ce0e035f65ba802c1b77 0.600000000000 1805531 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": 1317870, "vin": [ { "gen": { "height": 1317860 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74925ba3189366220a7559b0ccb5eaa69d3cd3ad0aa6ce0e035f65ba802c1b77" } } ], "extra": [ 1, 137, 191, 217, 138, 146, 181, 183, 231, 193, 248, 84, 1, 223, 15, 131, 66, 82, 141, 214, 168, 9, 116, 34, 220, 230, 57, 216, 210, 20, 186, 41, 238, 2, 17, 0, 0, 0, 12, 67, 132, 109, 102, 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