Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0e6c5b27dd169fdbdc206f00bd1ba691f0a8a7037183c75fcffeb31c3e12ce0

Tx prefix hash: d16e2e2f9c3b5c1b34166c8c4e73b6246123a886138f37127c64b4bbfa8ffecd
Tx public key: cd07de7403692379470a22def53aa30e56fdd8b67d399b523facb9753f806bd5
Timestamp: 1728138507 Timestamp [UCT]: 2024-10-05 14:28:27 Age [y:d:h:m:s]: 00:053:21:06:47
Block: 1125026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38499 RingCT/type: yes/0
Extra: 01cd07de7403692379470a22def53aa30e56fdd8b67d399b523facb9753f806bd5021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7da0f6397f98c1ef1f475d811d6ed7b6db636f0698d0d8878a8f41b5cbad055e 0.600000000000 1607699 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": 1125036, "vin": [ { "gen": { "height": 1125026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7da0f6397f98c1ef1f475d811d6ed7b6db636f0698d0d8878a8f41b5cbad055e" } } ], "extra": [ 1, 205, 7, 222, 116, 3, 105, 35, 121, 71, 10, 34, 222, 245, 58, 163, 14, 86, 253, 216, 182, 125, 57, 155, 82, 63, 172, 185, 117, 63, 128, 107, 213, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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