Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0da8cc87d447cb889f728a3566d27dbf01a20a0c8a9606cd66c14eb37d33a463

Tx prefix hash: 8e5b13ff8c4691665ca7d00dc5146c5014de235fd32c2000e319457aa2ca9e36
Tx public key: bd8405a96f4555e981a59d15277e3bd0be597a9e66e60371cd41e1fdc48c61fb
Timestamp: 1726458448 Timestamp [UCT]: 2024-09-16 03:47:28 Age [y:d:h:m:s]: 00:202:05:29:29
Block: 1111100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144354 RingCT/type: yes/0
Extra: 01bd8405a96f4555e981a59d15277e3bd0be597a9e66e60371cd41e1fdc48c61fb02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 768bcbbf01ad13043fd30876ea0af71c269c97872140eb35445fbdfe4a54a7a1 0.600000000000 1589943 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": 1111110, "vin": [ { "gen": { "height": 1111100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "768bcbbf01ad13043fd30876ea0af71c269c97872140eb35445fbdfe4a54a7a1" } } ], "extra": [ 1, 189, 132, 5, 169, 111, 69, 85, 233, 129, 165, 157, 21, 39, 126, 59, 208, 190, 89, 122, 158, 102, 230, 3, 113, 205, 65, 225, 253, 196, 140, 97, 251, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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