Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 016680df8c0822ca9fe170259dce0cd5a4b09c8732d40511d0bbce5da87b6d84

Tx prefix hash: 66ea5822bebbe60d08f0014dc8a1e786c7def51376f6f15cf77a18a235675e01
Tx public key: 3338ffbc319da1ef4c89e4a6bae4e397f5f3e6eda320b662b7df64fb3cd7fd1a
Timestamp: 1736477765 Timestamp [UCT]: 2025-01-10 02:56:05 Age [y:d:h:m:s]: 00:069:05:07:18
Block: 1194023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49265 RingCT/type: yes/0
Extra: 013338ffbc319da1ef4c89e4a6bae4e397f5f3e6eda320b662b7df64fb3cd7fd1a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a77182cfa7d4cead6e7c986a680d4ffdfab9d8f4a8f4d795d1829a02df95601 0.600000000000 1680590 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": 1194033, "vin": [ { "gen": { "height": 1194023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a77182cfa7d4cead6e7c986a680d4ffdfab9d8f4a8f4d795d1829a02df95601" } } ], "extra": [ 1, 51, 56, 255, 188, 49, 157, 161, 239, 76, 137, 228, 166, 186, 228, 227, 151, 245, 243, 230, 237, 163, 32, 182, 98, 183, 223, 100, 251, 60, 215, 253, 26, 2, 17, 0, 0, 0, 3, 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