Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e05b1826746f5f3485254a6f730f1fa39977c36d0f7523438f969a2ec446ff0

Tx prefix hash: 537d812929a823b300cc94941b7c097bc6e7b94d26de108908461b004f6b0167
Tx public key: 74f05bbae670610f41e5e7bfb00c4648282701d248f3e8fe769af1acfa92f18c
Timestamp: 1733146594 Timestamp [UCT]: 2024-12-02 13:36:34 Age [y:d:h:m:s]: 00:119:15:04:03
Block: 1166440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85303 RingCT/type: yes/0
Extra: 0174f05bbae670610f41e5e7bfb00c4648282701d248f3e8fe769af1acfa92f18c021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fcd3ba0c6e4b2b813759ca37b6ca4b78843a07cef83c20a67b4c3b5da3a0b89 0.600000000000 1652127 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": 1166450, "vin": [ { "gen": { "height": 1166440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fcd3ba0c6e4b2b813759ca37b6ca4b78843a07cef83c20a67b4c3b5da3a0b89" } } ], "extra": [ 1, 116, 240, 91, 186, 230, 112, 97, 15, 65, 229, 231, 191, 176, 12, 70, 72, 40, 39, 1, 210, 72, 243, 232, 254, 118, 154, 241, 172, 250, 146, 241, 140, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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