Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bedc146fe00a01fda30d631c129c6ff701a54b57e831464fe0a0400113f832f7

Tx prefix hash: 696811055137a50055f5e9cfba2df1d583d9f646467756a2bdee3ef6426e66bb
Tx public key: 6eed8d7556d0a4fe1e3605c967b2f13cfd449844ac4f1ae7b015581ad6f3e588
Timestamp: 1724607222 Timestamp [UCT]: 2024-08-25 17:33:42 Age [y:d:h:m:s]: 00:137:10:01:42
Block: 1095750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98289 RingCT/type: yes/0
Extra: 016eed8d7556d0a4fe1e3605c967b2f13cfd449844ac4f1ae7b015581ad6f3e58802110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ed718d91e55c638b508969b266d77cf4f1bdb7b313e9d0a51d64ee5f69bdb30 0.600000000000 1570931 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": 1095760, "vin": [ { "gen": { "height": 1095750 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ed718d91e55c638b508969b266d77cf4f1bdb7b313e9d0a51d64ee5f69bdb30" } } ], "extra": [ 1, 110, 237, 141, 117, 86, 208, 164, 254, 30, 54, 5, 201, 103, 178, 241, 60, 253, 68, 152, 68, 172, 79, 26, 231, 176, 21, 88, 26, 214, 243, 229, 136, 2, 17, 0, 0, 0, 10, 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