Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51a776ff80d4c51edd43156e09eb4239a316ed813d7ee74b07cb7d8687fcea35

Tx prefix hash: 74c28d0bb1f2a65cea91bf64e4c98d8412c5da6ded3432a19f35391c562a9af5
Tx public key: b4950541e71db7e1bb0899549980c68b3ebcf13754e93ea8d5a4b98806b8c1bc
Timestamp: 1681352268 Timestamp [UCT]: 2023-04-13 02:17:48 Age [y:d:h:m:s]: 01:353:15:15:54
Block: 737377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 514034 RingCT/type: yes/0
Extra: 01b4950541e71db7e1bb0899549980c68b3ebcf13754e93ea8d5a4b98806b8c1bc0211000000015029cbac000000000000000000

1 output(s) for total of 2.211893034000 dcy

stealth address amount amount idx
00: 45e326a08347c59de974a397fbfb5eb3c8a4e6e545e20d24c4b8bfacd692878d 2.211893034000 1183928 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": 737387, "vin": [ { "gen": { "height": 737377 } } ], "vout": [ { "amount": 2211893034, "target": { "key": "45e326a08347c59de974a397fbfb5eb3c8a4e6e545e20d24c4b8bfacd692878d" } } ], "extra": [ 1, 180, 149, 5, 65, 231, 29, 183, 225, 187, 8, 153, 84, 153, 128, 198, 139, 62, 188, 241, 55, 84, 233, 62, 168, 213, 164, 185, 136, 6, 184, 193, 188, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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