Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6716b6fa31935e6d772b7e5e7ccb3b7cdf1a89bb78ee0272076c3147cc5574c3

Tx prefix hash: 60280042b8d8e78f73485fe092018a59307c0ec48790f9028db1b1e081c44d20
Tx public key: b1bffe485fc86933d93581ac12a54fa5dac092be5b1c516e40d0b53697d91fe8
Timestamp: 1717660050 Timestamp [UCT]: 2024-06-06 07:47:30 Age [y:d:h:m:s]: 00:286:13:50:53
Block: 1038161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204821 RingCT/type: yes/0
Extra: 01b1bffe485fc86933d93581ac12a54fa5dac092be5b1c516e40d0b53697d91fe80211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17087f90b6f08924eec31e3ce4205063cff9dcc2ad410efdfb3fae5088dfc33d 0.600000000000 1506722 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": 1038171, "vin": [ { "gen": { "height": 1038161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17087f90b6f08924eec31e3ce4205063cff9dcc2ad410efdfb3fae5088dfc33d" } } ], "extra": [ 1, 177, 191, 254, 72, 95, 200, 105, 51, 217, 53, 129, 172, 18, 165, 79, 165, 218, 192, 146, 190, 91, 28, 81, 110, 64, 208, 181, 54, 151, 217, 31, 232, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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