Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58283be992094102146217e2c9600f3043799f93b56705be85c8092db4b24f0e

Tx prefix hash: 0b6e4325872068f4fdc871703362edd0e648776800ea98a6ce2835107ef53778
Tx public key: 183a869f81e19c0465b9e4cc28e5cd9c1b9b2c05eac173e2e9b5fa3e79c0e872
Timestamp: 1731161839 Timestamp [UCT]: 2024-11-09 14:17:19 Age [y:d:h:m:s]: 00:135:10:20:48
Block: 1150014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96593 RingCT/type: yes/0
Extra: 01183a869f81e19c0465b9e4cc28e5cd9c1b9b2c05eac173e2e9b5fa3e79c0e872021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4391a2224bf9d7b92af0512ab8deb98a156421e7170d4d23cb238547392092b4 0.600000000000 1635207 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": 1150024, "vin": [ { "gen": { "height": 1150014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4391a2224bf9d7b92af0512ab8deb98a156421e7170d4d23cb238547392092b4" } } ], "extra": [ 1, 24, 58, 134, 159, 129, 225, 156, 4, 101, 185, 228, 204, 40, 229, 205, 156, 27, 155, 44, 5, 234, 193, 115, 226, 233, 181, 250, 62, 121, 192, 232, 114, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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