Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ea8b3534244658941867ad4f620dac3dc4341a60d17e3959b7c9fda18819e45

Tx prefix hash: 56c99a2b7b4290be7838aa5191a58bd2829ce4a3330472c7dccce15402bcc442
Tx public key: 5b0583c11c2b5cf574a84d868a3ae55d8ac3947f283e715fb5795a59dc8ea7ac
Timestamp: 1685087117 Timestamp [UCT]: 2023-05-26 07:45:17 Age [y:d:h:m:s]: 01:336:00:26:39
Block: 768356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501378 RingCT/type: yes/0
Extra: 015b0583c11c2b5cf574a84d868a3ae55d8ac3947f283e715fb5795a59dc8ea7ac02110000000275e3f0e9000000000000000000

1 output(s) for total of 1.746295716000 dcy

stealth address amount amount idx
00: 8b5c1446dead141c0e618f033ac3f91af2c96a43c82e1751255c9b20c6bdb35b 1.746295716000 1217551 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": 768366, "vin": [ { "gen": { "height": 768356 } } ], "vout": [ { "amount": 1746295716, "target": { "key": "8b5c1446dead141c0e618f033ac3f91af2c96a43c82e1751255c9b20c6bdb35b" } } ], "extra": [ 1, 91, 5, 131, 193, 28, 43, 92, 245, 116, 168, 77, 134, 138, 58, 229, 93, 138, 195, 148, 127, 40, 62, 113, 95, 181, 121, 90, 89, 220, 142, 167, 172, 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