Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75822c205b55c927afa6c791ea215df5294454e279013e7c32b102b5a7e0e441

Tx prefix hash: 6724a21ee77f633641440eb21454c0104dfadadf4ff4e523ed46201895f93096
Tx public key: 37fe293e27d47df417f03e49f7c12d9486ff36fe93ad4f79b1190081a8b9cc7d
Timestamp: 1676241229 Timestamp [UCT]: 2023-02-12 22:33:49 Age [y:d:h:m:s]: 02:013:06:33:28
Block: 695670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 531041 RingCT/type: yes/0
Extra: 0137fe293e27d47df417f03e49f7c12d9486ff36fe93ad4f79b1190081a8b9cc7d02110000000733af99f4000000000000000000

1 output(s) for total of 3.040579921000 dcy

stealth address amount amount idx
00: 2ca83ea473d0897eb5bad18b2efe64a67eaa683cde039211faf22a3e1bc7e083 3.040579921000 1138627 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": 695680, "vin": [ { "gen": { "height": 695670 } } ], "vout": [ { "amount": 3040579921, "target": { "key": "2ca83ea473d0897eb5bad18b2efe64a67eaa683cde039211faf22a3e1bc7e083" } } ], "extra": [ 1, 55, 254, 41, 62, 39, 212, 125, 244, 23, 240, 62, 73, 247, 193, 45, 148, 134, 255, 54, 254, 147, 173, 79, 121, 177, 25, 0, 129, 168, 185, 204, 125, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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