Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b374e2c242bb52228b628bef227cac5300fa7f6e69e1779fda7328ea61bc218

Tx prefix hash: e6ed28540c9d84a0992455ded1fa89e6d8ef8814f8ed6edd0390aa5cd196661c
Tx public key: daec08a92000e5ce54e9ea1e76c3a710b91619d03aff38eacc35e4bcb84a8e2d
Timestamp: 1675527971 Timestamp [UCT]: 2023-02-04 16:26:11 Age [y:d:h:m:s]: 02:072:01:09:22
Block: 689750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 573107 RingCT/type: yes/0
Extra: 01daec08a92000e5ce54e9ea1e76c3a710b91619d03aff38eacc35e4bcb84a8e2d021100000002e6d27f9c000000000000000000

1 output(s) for total of 3.181059918000 dcy

stealth address amount amount idx
00: c5c3b0261dc4f811723ce881c91f86999279dd8a90b8713da8e98a293030d575 3.181059918000 1132444 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": 689760, "vin": [ { "gen": { "height": 689750 } } ], "vout": [ { "amount": 3181059918, "target": { "key": "c5c3b0261dc4f811723ce881c91f86999279dd8a90b8713da8e98a293030d575" } } ], "extra": [ 1, 218, 236, 8, 169, 32, 0, 229, 206, 84, 233, 234, 30, 118, 195, 167, 16, 185, 22, 25, 208, 58, 255, 56, 234, 204, 53, 228, 188, 184, 74, 142, 45, 2, 17, 0, 0, 0, 2, 230, 210, 127, 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