Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34fc540bdb934e5cdf2bb5664cbd942f655240ae80b59fab40f5ae0fab9af46a

Tx prefix hash: f6ae8ae43f021c0fb4b6b4669de68c53d4a101da071db9fa235391df934b5f9c
Tx public key: c8f2d87ccf7526f84afce94ed1514c73bdf7df47b6fafb971c48283d8f270525
Timestamp: 1708471945 Timestamp [UCT]: 2024-02-20 23:32:25 Age [y:d:h:m:s]: 01:118:12:45:52
Block: 961980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345673 RingCT/type: yes/0
Extra: 01c8f2d87ccf7526f84afce94ed1514c73bdf7df47b6fafb971c48283d8f2705250211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ff4f704caeb8c82d41e1814810ef669a555e7ab8ee8d30db0c0921c786049e0 0.600000000000 1421603 of 15

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": 961990, "vin": [ { "gen": { "height": 961980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ff4f704caeb8c82d41e1814810ef669a555e7ab8ee8d30db0c0921c786049e0" } } ], "extra": [ 1, 200, 242, 216, 124, 207, 117, 38, 248, 74, 252, 233, 78, 209, 81, 76, 115, 189, 247, 223, 71, 182, 250, 251, 151, 28, 72, 40, 61, 143, 39, 5, 37, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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