Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 403a1c576724a45cc986ed3c865f9c5e09dd99a6c780c2f613efe7227d39b3ce

Tx prefix hash: 088dc938b7a3b6d9c7435f962386447f34e9ca8af1aa3acb5aea342e6647bf46
Tx public key: 26f4d4cd11a2f8b6ef2de5b8f535ab93ac1861f2ef3dd2da70f5adb06154dff8
Timestamp: 1578238961 Timestamp [UCT]: 2020-01-05 15:42:41 Age [y:d:h:m:s]: 05:104:22:33:17
Block: 39297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1224898 RingCT/type: yes/0
Extra: 0126f4d4cd11a2f8b6ef2de5b8f535ab93ac1861f2ef3dd2da70f5adb06154dff802110000000edcee4b4d000000000000000000

1 output(s) for total of 454.787550338000 dcy

stealth address amount amount idx
00: dffe5fe535eb7a6be3cde20a9a640bb6593cbf6c3546f027d121252090555bf3 454.787550338000 67642 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": 39307, "vin": [ { "gen": { "height": 39297 } } ], "vout": [ { "amount": 454787550338, "target": { "key": "dffe5fe535eb7a6be3cde20a9a640bb6593cbf6c3546f027d121252090555bf3" } } ], "extra": [ 1, 38, 244, 212, 205, 17, 162, 248, 182, 239, 45, 229, 184, 245, 53, 171, 147, 172, 24, 97, 242, 239, 61, 210, 218, 112, 245, 173, 176, 97, 84, 223, 248, 2, 17, 0, 0, 0, 14, 220, 238, 75, 77, 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