Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7f83cdc045b0e68a05a549634fcf7b1572c9ca30b8cc8dc923cd6733339313c

Tx prefix hash: 0cdf24eacef56e3aa541fd925da6e378e4822badc52fccb3b3cb243c84c9d783
Tx public key: 3935da5fdff8242bcf5cfa18806acb73cd9b03fc77d35b397ba717c02a619a90
Timestamp: 1711578287 Timestamp [UCT]: 2024-03-27 22:24:47 Age [y:d:h:m:s]: 01:083:16:06:50
Block: 987749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320677 RingCT/type: yes/0
Extra: 013935da5fdff8242bcf5cfa18806acb73cd9b03fc77d35b397ba717c02a619a9002110000000e7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f49873b0b459f25f95949f2cfdcce90078d8c5275dbb5dfc03b322a4d8db2ade 0.600000000000 1448008 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": 987759, "vin": [ { "gen": { "height": 987749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f49873b0b459f25f95949f2cfdcce90078d8c5275dbb5dfc03b322a4d8db2ade" } } ], "extra": [ 1, 57, 53, 218, 95, 223, 248, 36, 43, 207, 92, 250, 24, 128, 106, 203, 115, 205, 155, 3, 252, 119, 211, 91, 57, 123, 167, 23, 192, 42, 97, 154, 144, 2, 17, 0, 0, 0, 14, 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