Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 992604da2e6e1a549d3ddc8d8d384185d96b572b25bd3f21b549cd6167739ae8

Tx prefix hash: e95f36c6cc091c3c5dc2fe1e4f9691500553777fb16c98e3e0f49b2e03ec856d
Tx public key: b90fac753d357dd68459aaaeb95a6761484225bfa283ba68fd2cc0daea155e4c
Timestamp: 1702381812 Timestamp [UCT]: 2023-12-12 11:50:12 Age [y:d:h:m:s]: 01:155:05:38:23
Block: 911509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372091 RingCT/type: yes/0
Extra: 01b90fac753d357dd68459aaaeb95a6761484225bfa283ba68fd2cc0daea155e4c02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb456dc6fbea7a029ed8a5a4cd31b09c0cf65f60919b12c3a5b2d278201f18e8 0.600000000000 1368713 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": 911519, "vin": [ { "gen": { "height": 911509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb456dc6fbea7a029ed8a5a4cd31b09c0cf65f60919b12c3a5b2d278201f18e8" } } ], "extra": [ 1, 185, 15, 172, 117, 61, 53, 125, 214, 132, 89, 170, 174, 185, 90, 103, 97, 72, 66, 37, 191, 162, 131, 186, 104, 253, 44, 192, 218, 234, 21, 94, 76, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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