Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43f6db62d525c7d27b777205a173701a1c6536490ca83d179b249a932ecf5dcf

Tx prefix hash: cece67c7d0410887a79afc44fbe8eaa92f25f9eec2962e162aad5f03f6a4e104
Tx public key: 6b133d609372e7210e5030fa758d8a3f84d76d0fba3d61b7fdb32bdf8069765b
Timestamp: 1673107151 Timestamp [UCT]: 2023-01-07 15:59:11 Age [y:d:h:m:s]: 02:100:13:45:21
Block: 669646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 593573 RingCT/type: yes/0
Extra: 016b133d609372e7210e5030fa758d8a3f84d76d0fba3d61b7fdb32bdf8069765b02110000000171bd5189000000000000000000

1 output(s) for total of 3.708384665000 dcy

stealth address amount amount idx
00: 694ed2c94a5e796ce279a9d6f4ff0370f311724dd9011275d54f28434b0f9d3c 3.708384665000 1110993 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": 669656, "vin": [ { "gen": { "height": 669646 } } ], "vout": [ { "amount": 3708384665, "target": { "key": "694ed2c94a5e796ce279a9d6f4ff0370f311724dd9011275d54f28434b0f9d3c" } } ], "extra": [ 1, 107, 19, 61, 96, 147, 114, 231, 33, 14, 80, 48, 250, 117, 141, 138, 63, 132, 215, 109, 15, 186, 61, 97, 183, 253, 179, 43, 223, 128, 105, 118, 91, 2, 17, 0, 0, 0, 1, 113, 189, 81, 137, 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