Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1132dbc1e44d30d9dacba656fd440397761c3532b7c73a850a2ef009a49acb3e

Tx prefix hash: 3c1162c21f614bcf4cd8bfe1b002628a27d5688897ba06671c07be526678c225
Tx public key: ef0b8609c782c33c9eddf83933cd9c9f093a89a53a714e7fa09e8df8d4d1a478
Timestamp: 1685462207 Timestamp [UCT]: 2023-05-30 15:56:47 Age [y:d:h:m:s]: 02:192:19:00:27
Block: 771469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 657615 RingCT/type: yes/0
Extra: 01ef0b8609c782c33c9eddf83933cd9c9f093a89a53a714e7fa09e8df8d4d1a478021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.705309151000 dcy

stealth address amount amount idx
00: 79358b705397eaa59db6ce86bbdfc4c1535221cf5c8e38f6ecf0537d4a184845 1.705309151000 1220838 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": 771479, "vin": [ { "gen": { "height": 771469 } } ], "vout": [ { "amount": 1705309151, "target": { "key": "79358b705397eaa59db6ce86bbdfc4c1535221cf5c8e38f6ecf0537d4a184845" } } ], "extra": [ 1, 239, 11, 134, 9, 199, 130, 195, 60, 158, 221, 248, 57, 51, 205, 156, 159, 9, 58, 137, 165, 58, 113, 78, 127, 160, 158, 141, 248, 212, 209, 164, 120, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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