Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b85bc4639b64b44dc4c361cca74ca70315b72430d854f44a1e68a64538a56dc9

Tx prefix hash: aaaa9123318b024feb8efa751cb6232f0bf76d445aa06f77cb0e56b33bccd044
Tx public key: 7f74ced4b15a4b2aab462518e977586a5dcfafd3d4dcb08bec6cd83adaca846d
Timestamp: 1722907613 Timestamp [UCT]: 2024-08-06 01:26:53 Age [y:d:h:m:s]: 00:246:13:12:52
Block: 1081657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176109 RingCT/type: yes/0
Extra: 017f74ced4b15a4b2aab462518e977586a5dcfafd3d4dcb08bec6cd83adaca846d02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88e5b81cf2b55ab301df800b9433e7c8d852a2ad5a5344c67fe9f0da397faf16 0.600000000000 1555474 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": 1081667, "vin": [ { "gen": { "height": 1081657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88e5b81cf2b55ab301df800b9433e7c8d852a2ad5a5344c67fe9f0da397faf16" } } ], "extra": [ 1, 127, 116, 206, 212, 177, 90, 75, 42, 171, 70, 37, 24, 233, 119, 88, 106, 93, 207, 175, 211, 212, 220, 176, 139, 236, 108, 216, 58, 218, 202, 132, 109, 2, 17, 0, 0, 0, 7, 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