Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd5d6cbf62613c206af2036c3817b457f34a223debfca5f8dd0a3a2de5aea1a4

Tx prefix hash: 2a24eefda82cf8b3a858852ee768649fe091e55af02bcc801b7c51cc3402529e
Tx public key: 25a096c3b218cc051da4f60ce546a0f54d7bda3ef9de1bea2dd08e9a1b31cffd
Timestamp: 1656928021 Timestamp [UCT]: 2022-07-04 09:47:01 Age [y:d:h:m:s]: 02:315:00:14:37
Block: 536359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 746306 RingCT/type: yes/0
Extra: 0125a096c3b218cc051da4f60ce546a0f54d7bda3ef9de1bea2dd08e9a1b31cffd021100000002faf35c9c000000000000000000

1 output(s) for total of 10.252272289000 dcy

stealth address amount amount idx
00: 7e7347bde39965c756d9b22dc3137a174330cfb42374f22438a818d547412ecf 10.252272289000 966108 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": 536369, "vin": [ { "gen": { "height": 536359 } } ], "vout": [ { "amount": 10252272289, "target": { "key": "7e7347bde39965c756d9b22dc3137a174330cfb42374f22438a818d547412ecf" } } ], "extra": [ 1, 37, 160, 150, 195, 178, 24, 204, 5, 29, 164, 246, 12, 229, 70, 160, 245, 77, 123, 218, 62, 249, 222, 27, 234, 45, 208, 142, 154, 27, 49, 207, 253, 2, 17, 0, 0, 0, 2, 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