Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b650d24ef76747c8732fbf6758b6e8c665ce8c34a2f25d7c8c5e4881f83a32bf

Tx prefix hash: ebbec603f5da0f772de4aa245076f6c40b6a83c102d526fa2921bca8c206714c
Tx public key: 2c1ed546a74241c2d34c84a1600fe75dbc5980c197549d647baedc00b4ad8da8
Timestamp: 1700287175 Timestamp [UCT]: 2023-11-18 05:59:35 Age [y:d:h:m:s]: 01:157:00:16:27
Block: 894119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373404 RingCT/type: yes/0
Extra: 012c1ed546a74241c2d34c84a1600fe75dbc5980c197549d647baedc00b4ad8da802110000000133af99f4000000000000000000

1 output(s) for total of 0.668979144000 dcy

stealth address amount amount idx
00: 40b48b272569aa82e8b54b335b5a1b373cc43de77ef5c29c113fe3d0fef23716 0.668979144000 1350310 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": 894129, "vin": [ { "gen": { "height": 894119 } } ], "vout": [ { "amount": 668979144, "target": { "key": "40b48b272569aa82e8b54b335b5a1b373cc43de77ef5c29c113fe3d0fef23716" } } ], "extra": [ 1, 44, 30, 213, 70, 167, 66, 65, 194, 211, 76, 132, 161, 96, 15, 231, 93, 188, 89, 128, 193, 151, 84, 157, 100, 123, 174, 220, 0, 180, 173, 141, 168, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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