Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac49484e10b0ca16b95f1772e58b7bf87f62575233fe4d78a14771cb85eec8f6

Tx prefix hash: 2bee1abbc8a148ac1d4409f9c37b3712352cefaffa6716fe8cb0182b7d2c5c97
Tx public key: 4fe942176cf90b1f94bbada94209ff6677fdc899bff4feb4778ed2d7a73288f8
Timestamp: 1696986319 Timestamp [UCT]: 2023-10-11 01:05:19 Age [y:d:h:m:s]: 01:138:23:29:22
Block: 866970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360320 RingCT/type: yes/0
Extra: 014fe942176cf90b1f94bbada94209ff6677fdc899bff4feb4778ed2d7a73288f8021100000001faf35c9c000000000000000000

1 output(s) for total of 0.822940669000 dcy

stealth address amount amount idx
00: c4cd2bbfcde2ef3e91f48aae93c97a84b6490a41762ec6a0c5dec40a9d8018b9 0.822940669000 1321610 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": 866980, "vin": [ { "gen": { "height": 866970 } } ], "vout": [ { "amount": 822940669, "target": { "key": "c4cd2bbfcde2ef3e91f48aae93c97a84b6490a41762ec6a0c5dec40a9d8018b9" } } ], "extra": [ 1, 79, 233, 66, 23, 108, 249, 11, 31, 148, 187, 173, 169, 66, 9, 255, 102, 119, 253, 200, 153, 191, 244, 254, 180, 119, 142, 210, 215, 167, 50, 136, 248, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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