Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3096de0775ef7a7991f248f068d90f18af08e8a5df7157090fd97f2c44a62fe9

Tx prefix hash: 953107e585ba97b187042b0d4155177270ac6a0b7fac7de33181ea1d23693efc
Tx public key: c04690b6b3bc2bcefcc45d3c4ab40cf0a7cd7c721dbf98e91ccf384cead3dbc9
Timestamp: 1702745977 Timestamp [UCT]: 2023-12-16 16:59:37 Age [y:d:h:m:s]: 01:127:22:09:25
Block: 914507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352564 RingCT/type: yes/0
Extra: 01c04690b6b3bc2bcefcc45d3c4ab40cf0a7cd7c721dbf98e91ccf384cead3dbc9021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98a70e24db709984cdea873721339fda51d28c852d788fbf7891c38fff733198 0.600000000000 1371823 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": 914517, "vin": [ { "gen": { "height": 914507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98a70e24db709984cdea873721339fda51d28c852d788fbf7891c38fff733198" } } ], "extra": [ 1, 192, 70, 144, 182, 179, 188, 43, 206, 252, 196, 93, 60, 74, 180, 12, 240, 167, 205, 124, 114, 29, 191, 152, 233, 28, 207, 56, 76, 234, 211, 219, 201, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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