Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f12f707955a36308b2e18d8cbba584d9b1877fdd04b190ca1b0933ea177152b4

Tx prefix hash: 216d9b61bd3f3504231af75e4ceb7333e9eb7caea957164913058e11e0099e3f
Tx public key: 788976e82619756f5296b80b641e84eddaca38c3d193a22efc7b77f001529a14
Timestamp: 1694717017 Timestamp [UCT]: 2023-09-14 18:43:37 Age [y:d:h:m:s]: 01:167:01:18:00
Block: 848132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380457 RingCT/type: yes/0
Extra: 01788976e82619756f5296b80b641e84eddaca38c3d193a22efc7b77f001529a1402110000000333af99f4000000000000000000

1 output(s) for total of 0.950137955000 dcy

stealth address amount amount idx
00: 5f0f0c4f77e170e85e3ab9eae9b4655aa4cd41d2ad77131e65a7a400a3444e5b 0.950137955000 1301716 of 0

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": 848142, "vin": [ { "gen": { "height": 848132 } } ], "vout": [ { "amount": 950137955, "target": { "key": "5f0f0c4f77e170e85e3ab9eae9b4655aa4cd41d2ad77131e65a7a400a3444e5b" } } ], "extra": [ 1, 120, 137, 118, 232, 38, 25, 117, 111, 82, 150, 184, 11, 100, 30, 132, 237, 218, 202, 56, 195, 209, 147, 162, 46, 252, 123, 119, 240, 1, 82, 154, 20, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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